rustc: Harmonize DefKind
and DefPathData
#118573
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Follow up to #118188.
DefPathData::(ClosureExpr,ImplTrait)
are renamed to matchDefKind::(Closure,OpaqueTy)
.DefPathData::ImplTraitAssocTy
is replaced withDefPathData::TypeNS(kw::Empty)
because both correspond toDefKind::AssocTy
.It's possible that introducing
(DefKind,DefPathData)::AssocOpaqueTy
instead could be a better solution, but that would be a much more invasive change.Const generic parameters introduced for effects are moved from
DefPathData::TypeNS
toDefPathData::ValueNS
, because constants are values.DefPathData
is no longer passed tocreate_def
functions to avoid redundancy.